Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove __enter__ and __exit__ from MemorySnapshotProfiler #611

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

daniellepintz
Copy link
Contributor

Summary: There is no need for MemorySnapshotProfiler to be a context manager since it conflicts with start_step and stop_step

Differential Revision: D51049497

Danielle Pintz added 2 commits November 6, 2023 15:47
Summary:
Allows user to configure a `start_step` for when to start recording memory history. Addressing YanjunChen329 's feedback that he would like to record memory history for a specific range of steps, e.g. step 500-503.

Also:
* improve docstrings
* add validation for params
* MemorySnapshot callback no longer needs to call `start` and `stop`

Differential Revision: D51048945
Summary: There is no need for MemorySnapshotProfiler to be a context manager since it conflicts with start_step and stop_step

Differential Revision: D51049497
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51049497

daniellepintz pushed a commit to daniellepintz/tnt that referenced this pull request Nov 7, 2023
Summary:

There is no need for MemorySnapshotProfiler to be a context manager since it conflicts with start_step and stop_step

Differential Revision: D51049497
daniellepintz pushed a commit to daniellepintz/tnt that referenced this pull request Nov 7, 2023
Summary:

There is no need for MemorySnapshotProfiler to be a context manager since it conflicts with start_step and stop_step

Differential Revision: D51049497
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants